Phase 1, Step 5a: What to Do

Transitioning to an ST 2110 IP fabric shifts "What to Do" from typical baseband checklist tasks into rigorous protocol verification, boundary enforcement, and logical modeling workflows. Executing these steps ensures the system design foundation is solid, verifiable, and prepared for a seamless project hand-off.

To establish a clean, risk-mitigated deployment path, the engineering team must actively prioritize the following execution steps during this upfront phase.

---

The Paradigm Shift: Baseband vs. ST 2110 Execution

Execution Focus	Legacy Baseband Approach	ST 2110 IP Bridge Reality
SOW Scope Protection	Manage physical cable runs and distribution change requests visually.	Audit logical device subscriptions, multicast scale, and control plane API integration boundaries to prevent unbudgeted software scope creep.
Engineering Hand-Off	Pass along a physical BNC run list, physical rack layouts, and single-line block drawings.	Deliver a unified multi-layer packet-routing topology, PTP clock trees, NMOS registry designs, and joint network architecture parameters.
Equipment & Margin Audit	Verify physical hardware chassis counts, BNC connector inventory, and basic power loads.	Validate exact SFP+/QSFP media modules, software license packages, and explicit control plane protocol compliance maps before procurement.
Emergency Recovery Logic	Patch out a failed DA or manually route around a broken processing card at a physical jackfield.	Enforce true SMPTE ST 2022-7 hitless path protection, ensuring dual, independent network fabrics route split streams simultaneously.
Drawing & Blueprint Logic	Draft standalone conceptual room layouts and independent functional baseband blocks.	Consolidate conceptual drawings directly into dense network synoptics, acclimating the client early to virtualized multicast paths over VLANs.

---

Core Execution Pillars for Engineering Alignment

To successfully finalize this phase and lock down the design, five foundational action items must be integrated into the engineering workflow:

• Continuous Contractual Scope Audit: Treat the Scope of Work (SOW) in the System Sale Agreement as a living engineering boundary. Cross-reference it immediately whenever the client requests new logical endpoints, extra audio streams, or control modifications to protect the project from untracked software expansion.
• Unified Technical Hand-Off: Ensure that all upfront discovery materials—including exact multi-vendor API capacities, switch port profiles, and bandwidth models—are structured and cleanly transferred to the core Engineering team before system building begins.
• Pre-Procurement Hardware & License Sign-Off: Require a locked Master Equipment List and an approved Margin Analysis prior to any purchasing. In IP deployments, this must explicitly match the hardware capabilities with required software licensing keys (e.g., enabling NMOS or adding ST 2110-30 audio channels).
• Architectural Resilience Planning: Define clear recovery paths for every critical system node. Ask how the facility returns to air instantly if a spine switch or primary grandmaster fails, mandating deterministic failovers rather than relying on manual software reconfigurations during an incident.
• Synchronized Synoptic Drafting: Apply the exact same structural drawing logic in early conceptual drawings that will be used in final network synoptics. Use these initial conceptuals as an educational tool to acclimate the client to reading multi-layered virtual multicast routing maps rather than old physical floor boxes.